Integrated surgical implant delivery system and method

ABSTRACT

A medical device identification system includes a medical device including an identifier and a sensor device configured to read the identifier of the medical device. The system further includes an output device configured to provide feedback related to the medical device and a monitoring system communicably coupled to the sensor device and the output device. The monitoring system is configured to identify the medical device based on the identifier of the medical device read by the sensor device and transmit feedback to the output device specific to the medical device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/088,069, filed Nov. 22, 2013, which is incorporated herein byreference in its entirety.

BACKGROUND

Traditional systems and methods for providing support for a surgicaloperation that involves a medical device (e.g., an implant to beinserted in the surgery, a tool used in the surgery, etc.) typicallyinclude pre-operation planning, providing support during the operation,and post-operation support. A product specialist for the medical devicemay provide such support for the use of the medical device throughoutthe surgical operation process.

The product specialist may provide various functions for a hospitalrelating to the medical device. The product specialist may be on-site toprovide the various functions. For example, the on-site productspecialist may provide the surgical staff support and training for usingthe medical device in a procedure (e.g., how to insert an implant into apatient, how to use one or more tools during a surgical operation,etc.). The on-site product specialist may also provide advisory servicesto a doctor relating to the use of the medical device. Further, theon-site product specialist may track inventory of the medical device inthe hospital and provide sales-related services. For example, theon-site product specialist may order more medical devices for thehospital, create an invoice charging the hospital for use of the medicaldevice, etc.

SUMMARY

One embodiment of the present disclosure relates to a medical deviceinventory tracking system. The system includes a shipping containerconfigured to contain a medical device. The system further includes asensor coupled to the shipping container and configured to detect thepresence of the medical device. The system further includes a processingcircuit integrated into the shipping container. The processing circuitis configured to receive a signal from the sensor and to perform anaction based upon the signal.

Another embodiment of the present disclosure relates to a system formonitoring a surgical procedure using a medical device in an operatingroom. The system includes a camera positioned in the operating room. Thesystem further includes a display positioned in the operating room. Thesystem further includes a telecommunications interface configured topermit a videoconference between personnel in the operating room and aproduct specialist associated with the medical device using the displayand the camera.

Yet another embodiment of the present disclosure relates to a method forproviding support to a surgical team conducting a procedure involving amedical device. The method includes providing a camera and a display.The method further includes establishing a video connection between theoperating room and a product specialist, wherein video of the productspecialist is provided on the display. The method further includes usingthe camera to provide video to the product specialist.

Alternative exemplary embodiments relate to other features andcombinations of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE FIGURES

The disclosure will become more fully understood from the followingdetailed description, taken in conjunction with the accompanyingfigures, wherein like reference numerals refer to like elements, inwhich:

FIG. 1 is an illustration of an operating room in which the systems andmethods described herein may be implemented, according to an exemplaryembodiment;

FIG. 2 is an illustration of an operating room including cameras andsensors for detecting a medical device, according to an exemplaryembodiment;

FIG. 3 is an example display for providing a video connection betweenpersonnel in an operating room and a product specialist, according to anexemplary embodiment;

FIG. 4 is a block diagram of a monitoring system integrated into theoperating room of FIG. 1 for tracking use of a medical device, accordingto an exemplary embodiment;

FIG. 5 is a flow chart of a process for providing various inventory andsales functions in response to a detected use of a medical device,according to an exemplary embodiment;

FIG. 6 is a flow chart of a process for providing a video connectionbetween personnel in an operating room and a product specialist,according to an exemplary embodiment;

FIG. 7 is a perspective view of a shipping container including multipletrays and medical devices, according to an exemplary embodiment;

FIG. 8 is an illustration of an operating room, including the shippingcontainer of FIG. 7 and cameras and sensors for detecting a medicaldevice from the shipping container, according to an exemplaryembodiment;

FIG. 9 is a block diagram of a tracking system integrated into theshipping container of FIG. 7 for tracking medical devices, according toan exemplary embodiment; and

FIG. 10 is a flow chart of a process for tracking medical device usageof a medical device removed from a shipping container, according to anexemplary embodiment.

DETAILED DESCRIPTION

Referring generally to the figures, systems and methods for trackingmedical device use and providing services related to the medical deviceare shown and described. The systems and methods described herein may beused in place of having an on-site product specialist. The systems andmethods described herein may be used to track the use and inventory ofmedical devices in a hospital, to set up simulcasts or videoconferenceswith a product specialist located remotely from the hospital, and toassist personnel in an operating room. The systems and methods allow aproduct specialist to assist with use of a medical device, but in anoff-site manner instead of being on-site.

In one embodiment, a system for monitoring a surgical procedure using amedical device in an operating room is described. The system includesone or more cameras positioned in the operating room, and one or moredisplays (e.g., monitors) positioned in the operating room. The systemincludes a telecommunications link configured to permit avideoconference between personnel in the operating room (e.g., surgeons)and a product specialist (or other person) associated with the medicaldevice. The videoconference is provided using the one or more displaysto present the product specialist to the surgeon and the one or morecameras for providing the product specialist with a view of theoperating room, including the patient, medical device, etc.

The monitoring system further includes a module for identifying themedical device, either by optical scanning by the cameras, imagerecognition, or an RFID reader configured to scan a RFID tag of themedical device. The monitoring system then identifies the productspecialist associated with the medical device along with other medicaldevice information. Further, the monitoring system tracks usage of themedical device and performs various functions such as updating aninventory of the medical device, generating an invoice for the medicaldevice being used, and generating an order to provide to a vendor,supplier, distributor, etc. for re-stocking the hospital with themedical device.

In another embodiment, a medical device inventory tracking system isdescribed. The system includes a shipping container configured tocontain one or more medical devices. The system further includes asensor coupled to the shipping container configured to detect thepresence of the medical devices. The system further includes aprocessing circuit integrated into the shipping container, configured toreceive a signal from the sensor when a medical device is taken andused, and to perform an action based on the signal. The action may beupdating an inventory, generating an invoice, generating an order toprovide to a vendor for re-stocking the hospital with the medicaldevice, or otherwise.

The medical device inventory tracking system includes a module foridentifying the medical device based on the signal from the sensor. Inone embodiment, the sensor is an RFID reader configured to scan an RFIDtag of the medical device. The tracking system may then perform variousfunctions such as updating an inventory of the medical device in theshipping container, generating an invoice for the medical device beingused, and generating an order to provide to a vendor, supplier,distributor, etc. for re-stocking the hospital with the medical device.

The monitoring system and tracking system as presented in the presentdisclosure may be used to provide various services to the hospital. Inone embodiment, one of the monitoring system and tracking system may beprovided for monitoring medical device usage. In another embodiment, thehospital may include both a monitoring system in an operating room and atracking system integrated with a shipping container to monitor medicaldevice usage, and the monitoring system and tracking system may work inconcert. In yet another embodiment, the monitoring system and trackingsystem may be implemented as a single system in the hospital. In yetother embodiments, some of the functionality of the monitoring system asdescribed below may be executed in the tracking system, and vice versa.It should be understood that any such combination of functionality ofthe monitoring system and tracking system described above fall withinthe scope of the present disclosure.

Referring to FIG. 1, an illustration of an operating room 100 in whichthe systems and methods described herein may be implemented is shown,according to an exemplary embodiment. Operating room 100 may generallybe an environment in which a surgical procedure is performed. While thesystems and methods described herein are described as implemented in anoperating room of a hospital, it should be understood that in otherexemplary embodiments, the systems and methods described herein may beimplemented in any other location.

Operating room 100 may be occupied by one or more surgeons 102 (e.g., asurgical team, or other personnel) and a patient 104. Operating room 100may include various equipment for assisting surgeons 102 with a surgicaloperation to be performed on patient 104. For example, operating room100 includes displays 106. Displays 106 may be configured to displayinformation, to provide video, or otherwise. For example, a surgeon 102may participate in a videoconference with a product specialist locatedremotely from operating room 100 via displays 106. As another example, asurgeon 102 may view information related to a medical device being usedin an operation on displays 106.

In one embodiment, displays 106 may be in various fixed locations inoperating room 100. For example, one display 106 is shown mounted on awall of operating room 100, and another display 106 is shown on a tableand may be connected to a computer including a processing circuitconfigured to control display 106. In other embodiments, displays 106may be temporarily or permanently positioned in operating room 100 by asurgeon 102 in any location (e.g., mounted or anchored to an instrumenttable, anchored in a position that allows the surgeon to view thedisplay while operating, etc.). Displays 106 may be displays of any typeof configuration (e.g., LCD, CRT display, etc.).

Operating room 100 may further include one or more remote devices 108.Remote devices 108 may be devices belonging to a surgeon 102 or may beassociated with operating room 100. Remote devices 108 may be, forexample, cell phones, tablets, laptop computers, or other handhelddevices. Remote devices 108 may be configured to display information ina similar manner to displays 106. For example, a remote device 108 suchas a tablet may be used in a videoconference. Remote devices 108 mayfurther be configured to provide support to surgeons 102 during anoperation. Remote devices 108 may be held by a surgeon 102 or mounted inan advantageous location for viewing by surgeons 102.

While not shown in FIG. 1, the operating room 100 environment mayfurther include other devices for providing sensory feedback to surgeons102. For example, operating room 100 may include speakers for providingauditory feedback (e.g., from a product specialist communicatingremotely with surgeons 102). As another example, one or more surgeonsmay have an earpiece, microphone, headset, or other devices useful forcommunications with a product specialist without being near a display106 or remote device 108.

Operating room 100 is shown to include a monitoring system 110 which maybe implemented in a computing device located in operating room 100 (orlocated remotely from operating room 100). Monitoring system 110 maygenerally be configured to monitor the activity in operating room 100.In the present embodiment, monitoring system 110 is configured tomonitor the use of one or more medical devices during an operation. Forexample, monitoring system 110 may be able to detect when a medicaldevice is being used or about to be used in an operation. Monitoringsystem 110 may identify the medical device and provide support inresponse, such as providing surgeons 102 with medical device details,setting up a videoconference or simulcast, or otherwise. As shown inFIG. 1, monitoring system 110 may be executed in a computer connected toa display 106, in other embodiments, monitoring system 110 may be in anytype of computing device local or remotely located from operating room100. The operation of monitoring system 110 is described in greaterdetail in FIG. 4.

Operating room 100 is further shown to include a plurality of cameras112. Cameras 112 may be configured to provide visual support during anoperation in operating room 100. For example, cameras 112 may recordvideo to be provided in a simulcast of an operation for a productspecialist. As another example, video or images captured by cameras 112may be used to detect or verify the use of a medical device in anoperation. Cameras 112 may further provide general monitoring servicesfor operating room 100 and the hospital. Input from cameras 112 may bereceived at monitoring system 110.

In addition to cameras 112, one or more webcams or remote devices 108may further be configured to provide monitoring services for operatingroom 100. While the present disclosure describes monitoring activitiesusing cameras 112, it should be understood that other devices with videocapabilities (e.g., webcams, cell phones, tablets, etc.) may be used toprovide monitoring services in addition to or in lieu of cameras 112.

Operating room 100 is further shown to include an RFID reader 114configured to detect an RFID tag. Referring also to FIG. 2, thedetection of a medical device using cameras 112 and RFID reader 114 inoperating room 100 is illustrated. Surgeon 102 is shown holding amedical device 202. Medical device 202 may be an implant, a tool, or thelike. Medical device 202 includes an RFID tag 204 which may be detectedby RFID reader 114. RFID reader 114 may be located in any position inoperating room 100 such that a medical device including an RFID tag tobe used in an operation is detected. For example, RFID reader 114 may belocated in a ceiling, wall, or floor of operating room 100, may becoupled to a computer, monitor, operating table, or any other equipmentin operating room 100, may be in a remote device 108 of a surgeon 102,or otherwise. In various embodiments, RFID reader 114 may beautomatically configured to scan for and detect medical devices, or asurgeon 102 may approach RFID reader 114 to manually scan the medicaldevice. In one embodiment, operating room 100 may include other sensorsin addition to or in place of RFID reader 114 for sensing the presenceof medical device 202.

Cameras 112 may be used instead of or in concert with RFID reader 114 toidentify medical device 202. For example, if medical device 202 includesa bar code, cameras 112 may be configured to capture video or images ofthe bar code, and a processing circuit associated with cameras 112(e.g., monitoring system 110) may read the bar code to identify themedical device. As another example, cameras 112 may capture images ofmedical device 202 and a processing circuit associated with cameras 112(e.g., monitoring system 110) may use object recognition to identifymedical device 202 without the use of an identifier associated withmedical device 202. Surgeon 102 may approach a camera 112 to have thecamera record an image or video of the medical device, or cameras 112may be configured to automatically record an image or video, andmonitoring system 110 may identify the device.

Referring now to FIG. 3, an example display 106 for providing a videoconnection between personnel in an operating room and a productspecialist is shown, according to an exemplary embodiment. Display 106may be used by a surgeon or other personnel to communicate with aproduct specialist and to view information related to an operation ormedical device. In the embodiment of FIG. 3, display 106 is describedwith respect to providing video and information relating to a medicaldevice, but display 106 may additionally include other informationrelevant to the personnel that is not related directly to the medicaldevice.

Display 106 may be connected to a camera 302 and sensor 304. Camera 302and sensor 304 may be coupled to display 106. Camera 302 may be, forexample, a webcam that feeds video or images to a viewer (e.g., aproduct specialist) located remotely from operating room 100. Camera 302may be used to provide a simulcast of the operation or of one or moresurgeons or other personnel. In other embodiments, there may not be acamera 302 local to display 106 and the video feed or images from one ormore of cameras 112 may be provided, or video from both cameras 112 andcamera 302 may be provided. Sensor 304 may be a configured to detect amedical device and may have a functionality similar to RFID reader 114as described above. In various embodiments, there may not be a sensor304 local to display 106, or sensor 304 may be used in place of RFIDreader 114.

Display 106 is shown to include a video 306 portion that allows asurgeon to communicate face-to-face with a product specialist. Video 306portion may include a live stream of the product specialist. Video 306portion may alternatively or additionally be used to show a tutorial orother instruction for using a medical device in an operation.

Display 106 is further shown to include other portions for providingmedical device information. For example, display 106 may include atraining 308 section, where the surgeon may view medical deviceinformation, instructions for using the medical device in an operation,other tools needed or requirements for using the medical device, etc.Display 106 may also include an inventory 310 section, where the surgeonmay view inventory-related information (e.g., how many medical devicesare in stock in the hospital, what medical devices are needed for thecurrent operation, etc.). Display 106 may further include other sectionsto provide information to the personnel. For example, inventory 310section may include information about an order to be placed to a vendor,distributor, supplier, etc. for replenishing a stock of a medical devicein the hospital, an invoice charging the hospital for use of a medicaldevice, or otherwise. As another example, display 106 may displayinformation provided by a product specialist.

It should be understood that while display 106 is shown as presentingvarious information relating to the medical device, some or all of thefeatures provided by display 106 may be alternatively or additionallyprovided on other devices. For example, some or all of the features ofdisplay 106 may be provided on a remote device 108 of a surgeon. Anynumber of displays and/or remote devices may be used in combination inoperating room 100 to provide the features described herein.

While display 106 is described with reference to being provided in anoperating room 100, it should be understood that a similar display maybe provided for an off-site product specialist. The display may providethe product specialist with a live view of operating room 100 and theoperation, along with inventory information of the hospital, medicaldevice information, and other relevant information. The productspecialist can then provide guidance for use of the medical device andfor the operation.

Referring now to FIG. 4, monitoring system 110 is shown in greaterdetail. Monitoring system 110 may generally be configured to monitoractivity in an operating room, including the use of one or more medicaldevices in the operating room. For example, monitoring system 110 mayidentify a medical device 202, set up a videoconference or simulcast inoperating room 100, update inventory, order and re-stock the medicaldevice, and provide other such services.

As shown in FIG. 1, monitoring system 110 may be implemented in acomputing system local to operating room 100; in other embodiments,monitoring system 110 may be located remotely from monitoring system110. Further, while monitoring system 110 is shown as a single system,it should be understood that some of the modules, databases, and othercomponents of monitoring system 110 may be located in differentlocations, computing devices, etc. (e.g., tracking system 900 asdescribed below).

Monitoring system 110 is shown to include a communications interface 408configured to communicate with various equipment, devices, and the like.Communications interface 408 may be configured to establish a wirelessor wired (e.g., USB) connection with any number of devices that mayprovide input for monitoring system 110. For example, communicationsinterface 408 may establish a connection with one or more cameras 112,RFID readers 114, various displays (e.g., displays 106 or remote device108), sensors, and other devices in operating room 100. Communicationsinterface 408 may further establish a connection with one or morevendors 440 (e.g., a medical device provider or distributor) and one ormore product specialists 442. Product specialists 442 may be personneltrained and verified to provide medical support relating to a medicaldevice. Product specialists 442 may be associated with one or morevendors, may be trained and funded by one or more vendors, or mayotherwise be associated with the vendors in any way.

While communications interface 408 is shown as a single interface, itshould be understood that monitoring system 110 may include a pluralityof interfaces for communicating with a plurality of devices. Forexample, communications interface 408 may include a first interfaceconfigured to establish a wired or local connection with cameras 112 andRFID reader 114, and a second interface configured to establish aconnection over a network with vendors 440 or product specialist 442.

Monitoring system 110 is shown to include a processing circuit 402including a processor 404 and memory 406. Processor 404 may beimplemented as a general purpose processor, an application specificintegrated circuit (ASIC), one or more field programmable gate arrays(FPGAs), a group of processing components, or other suitable electronicprocessing components. Memory 406 is one or more devices (e.g., RAM,ROM, flash memory, hard disk storage, etc.) for storing data and/orcomputer code for completing and/or facilitating the various user orclient processes, layers, and modules described in the presentdisclosure. Memory 406 may be or include volatile memory or non-volatilememory. Memory 406 may include database components, object codecomponents, script components, or any other type of informationstructure for supporting the various activities and informationstructures of the present disclosure. Memory 406 is communicablyconnected to processor 404 and includes computer code or instructionmodules for executing one or more processes described herein. Memory 406is shown to include various modules 410-426 for completing theactivities described herein.

Memory 406 is shown to include a device ID module 410. Device ID module410 is configured to identify a medical device based on input fromcameras 112, RFID reader 114, or other devices. In one embodiment,device ID module 410 may be configured to receive a signal from RFIDreader 114. RFID reader 114 may detect the medical device via an RFIDtag on the medical device, and an indication may be provided to deviceID module 410.

In one embodiment, device ID module 410 may use optical scanning toidentify a device (using object recognition or text recognitioncapabilities). Device ID module 410 may receive a video, image, a seriesof images, etc., from cameras 112. The video or images may include themedical device. Device ID module 410 may then use object recognition toidentify the type of medical device depicted in the video or images.Device ID module 410 may also or alternatively use text recognition toidentify text, a symbol, a label, or any other identifier on the medicaldevice, and use the identification to identify the medical device.

In one embodiment, device ID module 410 may identify the medical devicevia a bar code. For example, a bar code may be recognized by device IDmodule 410, a sensor 304 may be configured to scan a bar code of themedical device, or otherwise. Device ID module 410 may then identify themedical device based on the bar code.

In one embodiment, each medical device may include a unique deviceidentifier (e.g., each medical device may be numbered in a way thatallows for easy inventory tracking). Device ID module 410 may beconfigured to identify each medical device by its unique deviceidentifier, in addition to identifying the type of medical device. Theunique identifier may be stored on an RFID tag, indicated by a number orsymbol on the medical device, or otherwise.

Memory 406 is shown to include a device information module 412. Deviceinformation module 412 is configured to provide medical device supportfor an identified medical device. Device information module 412 mayprovide medical device properties, a preferred usage of the medicaldevice, a supplier or manufacturer of the medical device, or a productspecialist associated with the medical device. Device information module412 may retrieve medical device information stored in medical deviceinformation database 428 or another source.

In one embodiment, the information relating to the individual medicaldevice includes one or more product specialists associated with themedical device. The product specialist may be a designated persontrained to provide medical support for use of the medical device. Theproduct specialist information may be provided to video module 418 forsetting up a teleconference with the product specialist.

In one embodiment, device information module 412 may be used to verifyif the medical device is to be used in an operation. For example, deviceinformation module 412 may retrieve operation information from a patientinformation database 430. Patient information database 430 may storeinformation relating to patients and operations to be performed on thepatients. Device information module 412 may verify that the detectedmedical device should be used in the operation for the patient (e.g., ifthe right implant is selected for insertion, if the right tools are onhand for the operation, etc.).

In one embodiment, device information module 412 may provide trainingmaterials related to the medical device. The training materials may beinformation specific to the medical device (e.g., how to install animplant in a patient, how to use a particular tool, warnings, etc.).Device information module 412 may provide such training materials to thesurgeons in the operating room when the medical device is detected.Regardless of a hospital and its staff's attempt to anticipate usage ofmedical devices in individual situations, it is usually not possible toaccount for every possible situation. Device information module 412 maybe configured to provide such specific support for individualoperations.

Memory 406 is shown to include a camera module 414. Camera module 414 isconfigured to control the operation of cameras 112 (and other recordingdevices) in an operating room 100. Camera module 414 may work inconjunction with other modules to support the activities of monitoringsystem 110. For example, camera module 414 may be configured to recordvideo or images of a medical device for identification by device IDmodule 410. As another example, camera module 414 may be configured torecord the usage of a medical device during an operation for a simulcastgenerated by video module 418.

Memory 406 is shown to include a display module 416. Display module 416is configured to generate a user interface such as display 106 shown inFIG. 3. Display module 416 may work in conjunction with other modules tosupport the activities of monitoring system 110. For example, displaymodule 416 may display device information from device information module412, inventory information generated by inventory module 420, billinginformation generated by billing module 422, or information from patientinformation database 430. Display module 416 may display video of aproduct specialist 442 conducting a videoconference with a surgeon inoperating room 100. Display module 416 may further generate a userinterface that allows a user to manually enter information related tothe medical device (e.g., to request a product specialist, to manuallyupdate inventory, to look up medical device information, etc.).

Memory 406 is shown to include a video module 418. Video module 418 isconfigured to set up a videoconference with a product specialist 442,set up a simulcast of operating room 100, or provide other video-relatedfunctions. Video module 418 may set up a link with a product specialist442 identified by device information module 412.

In one embodiment, video module 418 may be configured to generate aconference including multiple product specialists. For example, anoperation may include a plurality of medical devices, and each medicaldevice may have a different product specialist. Monitoring system 110may identify and contact each product specialist, and video module 418may be configured to set up a conference such that the productspecialists may collaborate with the surgeons in the operating roomtogether.

Memory 406 generally includes inventory module 420, billing module 422,and ordering module 424 for providing sales services to the hospital.Modules 420-424 may generally be able to provide the same sales servicesan on-site product specialist normally provides. Modules 420-424 mayautomatically track inventory (instead of a product specialist manuallytracking), create invoices for medical device use (instead of a productspecialist manually generating the invoice), and generate orders forre-stocking the medical device (instead of a product specialistgenerating the order).

Memory 406 is shown to include an inventory module 420. Inventory module420 is configured to track inventory of medical devices in a hospital.Inventory module 420 may, upon detection of a medical device by deviceID module 410, update the inventory in the hospital (e.g., by indicatingthat the medical device is being used in an operation). Inventory module420 may further provide obsolescence tracking (e.g., tracking when amedical device is not wanted or used). Inventory module 420 may furthertrack an inventory history relating to the medical device. Inventorymodule 420 may update an inventory database 426. Inventory database 426may be accessible by any computer system and may provide up-to-dateinformation relating to the current stock of medical devices in thehospital, in the operating room, in a shipping container, or otherwise.

Memory 406 is shown to include a billing module 422. Billing module 422is configured to generate an invoice for use of a medical device duringan operation. For example, device ID module 410 may detect the usage ofan implant in an operation. Billing module 422 may then generate aninvoice charging the hospital for use of the implant. Billing module 422may be configured to generate an invoice for each medical device, or maygenerate an invoice for the use of several medical devices over time.

Memory 406 is shown to include an ordering module 424. Ordering module424 is configured to generate an order for one or more medical devicesto provide to a vendor 440. In one embodiment, ordering module 424 maycheck inventory database 426 to determine the current stock of variousmedical devices in a hospital. If the stock of a particular medicaldevice is running low or is out, ordering module 424 may be configuredto automatically generate an order to replenish the stock of the medicaldevice. In another embodiment, ordering module 424 may be configured togenerate an order for one or more medical devices based on a user (e.g.,surgeon) input. In another embodiment, ordering module 424 may beconfigured to provide a notification that an inventory of a medicaldevice needs to be replenished.

In one embodiment, inventory module 420 and ordering module 424 may beconfigured to track usage of medical devices in a hospital. Inventorymodule 420 may track usage of medical devices in a hospital (as theinventory is updated), and ordering module 424 may be able to predictfuture usage of medical devices or develop a schedule for replacing astock of medical devices in a hospital based on the usage. For example,when the stock of a medical device is reduced, ordering module 424 maypredict when an order needs to be submitted to a vendor 440 so that thehospital does not run out of the medical device. Ordering module 424 maygenerate a medical device replacement schedule which allows for ordergeneration on a scheduled basis.

Referring to FIG. 5, a flow chart of a process 500 for providing variousinventory and sales functions in response to a detected use of a medicaldevice is shown, according to an exemplary embodiment. Process 500 maybe executed by monitoring system 110 and more particularly modules420-424 for providing services related to the medical device usage.Process 500 generally includes a detection step and several subsequentsteps that may be executed based on the detection step. While process500 illustrates several steps 504-512 in response to the detection of amedical device, it should be understood that some of steps 504-512 maynot be executed, steps 504-512 may be executed in any order, orotherwise.

Process 500 includes detecting the use of the medical device (step 502).The use of the medical device may be detected in an operating room by amonitoring system. The medical device may include a RFID tag readable bya RFID reader, a bar code readable by a camera and monitoring system, orany other identifier configured to be readable by a monitoring system.

Process 500 includes updating an inventory of the medical device (step504). Step 504 may generally include detecting the use of a medicaldevice in an operation and updating the inventory in an inventorydatabase as needed (e.g., if the medical device is implanted into apatient). Step 504 may further include detecting if a medical device isreplaced or not used in an operation after an initial identification ofthe medical device.

Process 500 further includes generating an invoice for the hospital(step 506). The invoice charges the hospital for use of the medicaldevice. In various embodiments, the invoice may be for use of a singlemedical device, or may be for the use of many medical devices,accumulated over time. Step 506 may include using current inventoryinformation to determine when to generate the invoice. Step 506 mayfurther include using other information (e.g., an invoice schedule, aparticular date or time, etc.) to determine when to generate theinvoice.

Process 500 further includes generating a report for a supplier (step508). The report may generally relate to medical device usage in thehospital. For example, the report may indicate the current inventory inthe hospital, outstanding invoices and other billing information relatedto the hospital, the operations the medical devices were used in, orotherwise. In various embodiments, reports may be generated on ascheduled basis or on a per-use basis. Step 508 may further includegenerating an order for more medical devices.

Process 500 further includes retrieving medical device information (step510) and displaying the medical device information (step 512). Forexample, process 500 may be executed during an operation in an operatingroom. Steps 510-512 may include retrieving information relevant to thecurrent operation and displaying the information on a monitor in theoperating room in order to assist the surgeon in the operating room.

Referring to FIG. 6, a flow chart of a process 600 for providing a videoconnection between personnel in an operating room and a productspecialist is shown, according to an exemplary embodiment. Process 600may be executed by monitoring system 110 and more particularly modules410-418 for providing services related to the medical device usage.Process 600 generally includes a detection step and several subsequentsteps that may be executed based on the detection step. While process600 illustrates several steps 604-608 in response to the detection of amedical device, it should be understood that some of steps 604-608 maynot be executed, steps 604-608 may be executed in any order, orotherwise.

Process 600 includes detecting the use of a medical device (step 602).The use of the medical device may be detected in an operating room by amonitoring system. The medical device may include a RFID tag readable bya RFID reader, a bar code readable by a camera and monitoring system, orany other identifier configured to be readable by a monitoring system.Additionally or alternatively, step 602 may include a user request orother input relating to the medical device (e.g., a request for helprelating to the medical device).

Process 600 includes identifying the medical device and a productspecialist associated with the medical device (step 604). Step 604 mayinclude identifying medical device information, a vendor or supplier ofthe medical device, and other information related to the medical device.The identification of such information may be made using a uniqueidentifier of the medical device.

Process 600 includes establishing a communications link with the productspecialist (step 606) and setting up a videoconference between theoperating room and the product specialist (step 608). The productspecialist may then provide advisory services to a surgeon for medicaldevice usage, may monitor an operation, may provide live training forusing the medical device, and provide other services “live” in the samemanner that an on-site product specialist could.

Referring generally to FIGS. 1-6, a monitoring system is described thatmay be implemented in an operating room for tracking medical deviceusage. Alternatively or additionally, medical device usage may betracked via shipping containers in which the medical devices are shippedto the hospital. A processing circuit integrated with the shippingcontainer may be configured to track medical device usage by trackingwhen a medical device is removed from the shipping container. Theprocessing circuit integrated with the shipping container may thenprovide various services relating to the medical device. For example,the processing circuit may be useful for sales (e.g., for orderingmedical devices when the inventory runs low in the shipping container),inventory, quality control, obsolescence tracking (e.g., when a medicaldevice is no longer usable), surgical training, and more.

Referring now to FIG. 7, a shipping container 700 for medical devices isshown, according to an exemplary embodiment. Shipping container 700includes a plurality of trays 708, each tray including one or moremedical devices 710. Each medical device 710 may include an identifier712. Each identifier 712 may be unique to its medical device 710. Forexample, each identifier may be numbered individually such that theindividual device may be identified. As another example, identifiers 712may be RFID tags with information unique to the medical device.Additionally, each tray 708 may include an identifier such as an RFIDtag. The identifier for each tray 708 may include information relatingto the individual contents of each tray.

As described above, the identifiers may be RFID tags. In one embodiment,the RFID tags may be a read/write tag that may be altered by the shipperbefore shipping container 700 is sent to a hospital, and may be alteredby shipping container 700 when medical devices are removed. In anotherembodiment, the RFID tags may be a read-only tag to be replaced inshipping container 700 before each shipment.

Shipping container 700 is further shown to include a tracking system 702configured to support the tracking activities of shipping container 700.Shipping container 700 further includes a display 704 on which medicaldevice information may be displayed. Display 704 may include a monitor,lights, or any other type of display that provides information to a userrelating to a current status of the content of shipping container 700.For example, display 704 may provide information relating to the removalof a medical device when the removal occurs. Shipping container 700further includes an RFID reader 706 configured to read RFID tags.Shipping container 700 may alternatively or additionally include othersensors for tracking medical devices. While shipping container 700illustrates a single RFID reader 706, in various embodiments, shippingcontainer 700 may include any number of RFID readers.

Medical devices 710 may be shipped in shipping container 700 in one oftwo conditions. In one embodiment, each medical device may be sterilelypackaged in a disposable or reusable container. The sterile packagingmay contain individual RFID chips and/or visual identifiers such as abar code or number. RFID reader 706 may be configured to detect eachmedical device 710 using the RFID chips, while a surgeon or other usermay verify the correct medical device was chosen based on the visualidentifier. In another embodiment, each medical device may be deliveredin a tray 708 suitable for steam or gas sterilization. Each tray may bepositioned such that the removal of the tray or any of its medicaldevices is automatically detected by RFID reader 706.

RFID reader 706 may detect the removal of one or more medical devices710. Trays 708 and medical devices 710 may be positioned in shippingcontainer 700 in such a way that the removal of a medical device 710results in the detection of an identifier 712 by RFID reader 706.Further, RFID reader 706 may be configured to detect an identifierassociated with a tray 708 to determine the current contents of thetray. Upon detection of an RFID tag by RFID reader 706, a signal may besent to tracking system 702 for updating the inventory of shippingcontainer 700 and providing services related to the removed medicaldevice 710. In one embodiment, RFID reader 706 may detect the additionof one or more medical devices 710 to shipping container 700 as well.

Referring also to FIG. 8, shipping container 700 is shown in operatingroom 100. In one embodiment, shipping container 700 may be located inoperating room 100, and the tracking system of shipping container 700may work in concert with monitoring system 110 of operating room 100. Inanother embodiment, shipping container 700 may be located remotely fromoperating room 100, but the tracking system of shipping container 700may still work in concert with monitoring system 110. In yet anotherembodiment, the tracking system of shipping container 700 may operateindependent of monitoring system 110.

In the embodiment of FIG. 8, a surgeon 102 removes a medical device 710from shipping container 700. RFID reader 706 may detect the removal ofmedical device 710 via identifier 712 and may provide a signal totracking system 702. Further, cameras 112 and/or RFID reader 114 ofoperating room 100 may also detect medical device 710 via identifier 712or other identification methods. Tracking system 702 may be connected tocameras 112 and RFID reader 114 and verify the usage of medical device710. Alternatively, a monitoring system 110 may verify the use, ormonitoring system 110 and tracking system 702 may verify the detectionwith one another.

Referring now to FIG. 9, a tracking system 702 integrated with shippingcontainer 700 is shown, according to an exemplary embodiment. Trackingsystem 702 may generally be configured to monitor activity related toshipping container 700, including the removal and use of one or moremedical devices 710. For example, tracking system 702 may updateinventory, identify a medical device 710 being removed and used,identify a product specialist associated with the removed medical device710, and such services.

As shown in FIG. 7, tracking system 702 may be implemented as part of acomputing system integrated with shipping container 700; in otherembodiments, tracking system 702 may be implemented remotely fromshipping container 700. Further, while tracking system is shown as asingle system, it should be understood that some of the modules,databases, and other components of tracking system 702 may be located indifferent locations, computing devices, etc. (e.g., in monitoring system110).

Tracking system 702 is shown in FIG. 7 as a system that may provide theservices described in the present disclosure independently. In otherembodiments, tracking system 702 may work in concert with monitoringsystem 110, or may provide some of the same functionality as monitoringsystem 110.

Tracking system 702 includes a processing circuit 902 including aprocessor 904 and memory 906. Tracking system 702 further includes acommunications interface 908 configured to communicate with communicatewith various equipment, devices, and the like. Communications interface908 may be configured to establish a wireless or wired (e.g., USB)connection with any number of local devices (e.g., display 704, RFIDreader 706), remote systems (e.g., monitoring system 110) or outsidesources (e.g., vendor 440, product specialist 442, etc.). Processingcircuit 902, processor 904, memory 906, and communications interface 908may have the same general functionality as described above withreference to FIG. 4.

While communications interface 908 is shown connected to a plurality ofdevices and sources, communications interface 908 may further beconnected to remote displays 106, remote devices 108, or other devices.If tracking system 702 is configured to control a simulcast orvideoconference with an off-site product specialist, communicationsinterface 908 may be configured to establish a wireless communicationslink with displays 106, remote devices 108, cameras 112, or RFID reader114.

Memory 906 is shown to include a device ID module 910. Device ID module910 is configured to identify a medical device based on a signal fromRFID reader 706. RFID reader 706 may detect a medical device via an RFIDtag on the medical device as the medical device is removed from shippingcontainer 700. In one embodiment, each medical device may include aunique RFID tag. Device ID module 410 may be configured to identify eachmedical device by its unique RFID tag. In another embodiment, device IDmodule 910 may be configured to identify a medical device based on aninput from another sensor, camera, etc., using object recognition ortext recognition.

Memory 906 is shown to include a tray ID module 912. Tray ID module 912is configured to identify a tray 708 in shipping container 700 via anRFID tag (or other identifier). Tray ID module 912 may use the RFID tagto determine the current contents of tray 708. Tray ID module 912 mayfurther write information to an RFID tag of a tray 708. For example, ifthe contents of a tray are changed (e.g., a medical device is removedfrom the tray), tray ID module 912 may be configured to receive a signalfrom RFID reader 706 related to the removal of the medical device. TrayID module 912 may then cause information stored on the RFID tag of thetray to be updated (e.g., the inventory of the tray). Similarly, if amedical device is placed on a tray, the signal may be sent to tray IDmodule 912 and the information on the RFID tag of the tray may beupdated.

Memory 906 is shown to include device information module 914. Deviceinformation module 914 is configured to provide medical device supportfor a removed medical device. Device information module 914 may identifymedical device properties, preferred usage of the medical device, orsupplier or product specialist information associated with the medicaldevice. Device information module 914 may pull information from aninventory database 924 or medical device information database 926.Inventory database 924 may store current inventory information for theshipping container. Medical device information database 926 may storeinformation such as an associated vendor and product specialist for eachmedical device.

In one embodiment, the information relating to the individual medicaldevice includes one or more product specialists associated with themedical device. The product specialist may be a designated persontrained to provide medical support for use of the medical device. Theproduct specialist information may be used to contact the productspecialist for setting up a teleconference with the product specialiston a remote display.

In one embodiment, device information module 914 may be used to verifyif the medical device is to be used in an operation. For example, deviceinformation module 914 may retrieve operation information and use theinformation to verify that the correct medical device was removed fromshipping container 700. If the wrong medical device was taken, display704 may display the information, or the information may be sent to aremote display.

Memory 906 is shown to include a display module 916. Display module 916may be configured to control a display 704 associated with shippingcontainer 700. In one embodiment, display 704 may be a displayintegrated with shipping container 700. In other embodiments, display704 may be a display detachable from shipping container 700, may be adisplay located near shipping container 700, or may be a remote displayconfigured to display information for one or more shipping containers.Display module 916 may be configured to generate a display providinginventory information, medical device information, and other informationgenerated by the modules of tracking system 702.

While not shown in FIG. 9, memory 906 may additionally include a cameramodule and/or video module for controlling cameras and other equipmentlocated remotely from tracking system 702. For example, if an operatingroom includes tracking system 702 and not an independent monitoringsystem 110, tracking system 702 may include the camera module and/orvideo module as described in FIG. 4 to control the operation of thecameras and to provide telecommunications with an off-site productspecialist.

Memory 906 generally includes inventory module 918, billing module 920,and ordering module 922 for providing sales services to the hospital.Modules 918-922 may generally be able to provide the same sales servicesan on-site product specialist can. Modules 918-922 may automaticallytrack inventory (instead of a product specialist manually tracking),create invoices for medical device use (instead of a product specialistmanually generated invoice), and generate orders for re-stocking themedical device (instead of a product specialist).

Memory 906 is shown to include an inventory module 918. Inventory module918 is configured to track inventory of shipping container 700.Inventory module 918 may, upon detection of removal of a medical device,update the inventory in inventory database 924. Inventory database 924may be accessible by any computer system and may provide up-to-dateinformation relating to the current stock of medical devices in thehospital to any number of systems. For example, inventory module 918 mayprovide inventory information upon arrival of shipping container 700 toa hospital or vendor.

Memory 406 is shown to include a billing module 920. Billing module 920is configured to generate an invoice for use of a medical device. Forexample, billing module 920 may be configured to generate an invoicecharging the hospital for use of a medical device when the medicaldevice is removed from shipping container 700. Billing module 920 may beconfigured to wait for confirmation of use of the medical device beforegenerating the invoice. Alternatively, billing module 920 may beconfigured to generate an invoice for more than one medical devices, forall medical devices in shipping container 700, or otherwise.

Memory 406 is shown to include an ordering module 922. Ordering module922 is configured to generate an order for one or more medical devicesto provide to a vendor 440. In one embodiment, ordering module 922 maycheck inventory database 924 to determine the current stock of medicaldevices in shipping container 700. If the stock is low or out inshipping container 700, ordering module 922 may be configured toautomatically generate an order to provide to vendor 440 to replenishthe stock of the medical device. In one embodiment, ordering module 922may use a medical device usage rate, an estimated shipping time, or anyother information that may impact the availability of medical devices inthe hospital to determine when to generate an order.

In one embodiment, ordering module 922 may use inventory informationfrom other shipping containers or other hospital inventory information(e.g., inventory database 426 of monitoring system 110) to determine thecurrent stock of a medical device. Ordering module 922 may be configuredto use all such inventory information to determine if and when an ordershould be generated. In another embodiment, ordering module 922 may beconfigured to provide a notification that an inventory of a medicaldevice needs to be replenished before generating an order.

Referring to FIG. 10, a flow chart of a process 1000 for trackingmedical device usage using a processing circuit of the shippingcontainer is shown, according to an exemplary embodiment. Process 1000may be executed by tracking system 702 and more particularly modules910-922 for providing services related to the medical device usage.Process 1000 generally includes a detection step and several subsequentsteps that may be executed based on the detection step. While process1000 illustrates several steps 1006-1012 in response to the detection ofa medical device, it should be understood that some of steps 1006-1012may not be executed, steps 1006-1012 may be executed in any order, orotherwise.

Process 1000 includes detecting the removal of the medical device fromthe shipping container (step 1002). The detection of the medical devicemay be achieved via a RFID reader or other sensor integrated with theshipping container. Process 1000 may further include receiving anindication of usage of the medical device (step 1004). Such anindication may be received from a monitoring system, for example. Inanother embodiment, step 1004 may be skipped and steps 1006-1012 may beexecuted upon detection of removal of the medical device at step 1002.

Process 1000 includes recording usage of the medical device and updatingan inventory of the shipping container (step 1006). Step 1006 maygenerally include updating an inventory database of the shippingcontainer. Step 1006 may further include updating an overall inventoryof the medical device in the hospital.

Process 1000 further includes generating an invoice for the hospital(step 1008). The invoice charges the hospital for use of the medicaldevice. In various embodiments, the invoice may be for use of a singlemedical device, or may be for the use of many medical devices,accumulated over time. Step 1008 may include using current inventoryinformation of the shipping container to determine when to generate theinvoice. Step 506 may further include using other information (e.g., aninvoice schedule, a particular date or time, etc.) to determine when togenerate the invoice.

Process 1000 further includes generating a report for a supplier (step1010). The report may generally relate to medical device usage in thehospital. For example, the report may indicate the current inventory inthe shipping container, outstanding invoices and other billinginformation related to the shipping container, or otherwise. In variousembodiments, reports may be generated on a scheduled basis or on aper-use basis.

Process 1000 further includes generating an order for medical devicesfor a supplier (step 1012). The order may replenish the stock of themedical device in the hospital. In one embodiment, the order may begenerated when the shipping container is out of medical devices orreaches a minimum threshold of medical devices.

As described above, monitoring system 110 and/or tracking system 702 mayprovide various medical device-related services for a hospital. In oneembodiment, a plurality of tracking systems for each shipping containerin a hospital may be used to provide the features described herein. Anycombination of monitoring systems and tracking systems (including theomission of a monitoring system or tracking system) may be used toprovide the features described herein.

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. Other substitutions, modifications, changes, andomissions may be made in the design, operating conditions andarrangement of the exemplary embodiments without departing from thescope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, networked systems or by a hardwired system. Embodiments withinthe scope of the present disclosure include program products comprisingmachine-readable media for carrying or having machine-executableinstructions or data structures stored thereon. Such machine-readablemedia can be any available media that can be accessed by a generalpurpose or special purpose computer or other machine with a processor.By way of example, such machine-readable media can comprise RAM, ROM,EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to carry or store desired program code in the form ofmachine-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer or othermachine with a processor. When information is transferred or providedover a network or another communications connection (either hardwired,wireless, or a combination of hardwired or wireless) to a machine, themachine properly views the connection as a machine-readable medium.Thus, any such connection is properly termed a machine-readable medium.Combinations of the above are also included within the scope ofmachine-readable media. Machine-executable instructions include, forexample, instructions and data which cause a general purpose computer,special purpose computer, or special purpose processing machines toperform a certain function or group of functions. The machine-executableinstructions may be executed on any type of computing device (e.g.,computer, laptop, etc.) or may be embedded on any type of electronicdevice (e.g., a portable storage device such as a flash drive, etc.).

Although the figures may show a specific order of method steps, theorder of the steps may differ from what is depicted. Also, two or moresteps may be performed concurrently or with partial concurrence. Suchvariation will depend on the software and hardware systems chosen and ondesigner choice. All such variations are within the scope of thedisclosure. Likewise, software implementations could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps and decision steps.

What is claimed is:
 1. A medical device identification system,comprising: a medical device including an identifier; and a sensordevice configured to read the identifier of the medical device; anoutput device configured to provide feedback related to the medicaldevice; and a monitoring system communicably coupled to the sensordevice and the output device, the monitoring system configured to:identify the medical device based on the identifier of the medicaldevice read by the sensor device; and transmit feedback to the outputdevice specific to the medical device.
 2. The system of claim 1, whereinthe feedback includes at least one of operation information, medicaldevice details, a step to perform in an operation with the medicaldevice, training materials related to the medical device, and an alertin response to an improper medical device being for the operation. 3.The system of claim 1, wherein the identifier includes at least one ofan RFID tag, a structure of the medical device, a bar code, a text, asymbol, a label, and a number.
 4. The system of claim 3, wherein theidentifier is unique to a component designed specifically for a patient,and wherein the feedback is specific to the specifically designeddevice.
 5. The system of claim 3, wherein the identifier is a genericidentifier for a type of device, and wherein the feedback is directed tothe selected type of device.
 6. The system of claim 1, wherein thesensor device includes an RFID reader configured to detect and read anRFID tag of the medical device, wherein the monitoring system isconfigured to identify the medical device based on the RFID tag of themedical device.
 7. The system of claim 1, wherein the sensor deviceincludes a camera configured to capture at least one of a picture and avideo of the medical device.
 8. The system of claim 7, wherein themonitoring system is configured to identify the medical device using atleast one of object recognition, text recognition, symbol recognition,and bar code recognition on the at least one of the picture and thevideo of the medical device.
 9. The system of claim 1, wherein theoutput device includes at least one of a stationary display and aportable display configured to provide visual feedback.
 10. The systemof claim 1, wherein the medical device includes at least one of amedical implant and a surgical tool.
 11. The system of claim 1, whereinthe sensor device is further configured to track movement of the medicaldevice during use, and wherein the monitoring system is furtherconfigured to update the feedback instructions based on the movement ofthe medical device.
 12. A method for identifying and tracking a medicaldevice in an operation, comprising: detecting, by a sensor device, amedical device being used in an operation; reading, by the sensordevice, an identifier of the medical device; identifying, by aprocessing circuit, the medical device based on the identifier of themedical device; and providing, by the processing circuit via an outputdevice, feedback specific to the medical device in response to themedical device being used in the operation.
 13. The method of claim 12,wherein the feedback includes at least one of operation information,medical device details, a step to perform in the operation with themedical device, training materials related to the medical device, and analert.
 14. The method of claim 13, wherein the identifier is unique to adevice designed specifically for a patient, and wherein the feedback isspecific to the specifically designed device.
 15. The method of claim13, wherein the identifier is a generic identifier for a type of device,and wherein the feedback is directed to the selected type of device. 16.The method of claim 12, wherein the identifier includes at least one ofan RFID tag, a structure of the medical device, a bar code, a text, asymbol, a label, and a number.
 17. The method of claim 12, wherein thesensor device includes an RFID reader configured to detect and read anRFID tag of the medical device, wherein the processing circuit isconfigured to identify the medical device based on the RFID tag of themedical device.
 18. The method of claim 12, wherein the sensor deviceincludes a camera configured to capture at least one of a picture and avideo of the medical device.
 19. The method of claim 18, wherein theprocessing circuit is configured to identify the medical device using atleast one of object recognition, text recognition, and bar coderecognition on the at least one of the picture and the video of themedical device.
 20. The method of claim 12, further comprising:tracking, by the sensor device, movement of the medical device duringthe operation; and updating, by the processing circuit, the feedbackbased on the movement of the medical device during the operation.